@MhmRhm Can you have a look at #85 and tell me if it's needed or necessary to move minmea.h to include/? I kinda enjoy having the file in the root of the repository, and my knowledge of CMake is exactly zero, so I would love if someone with more knowledge would share their thoughts.

To the best of my knowledge, the main reason is that this is the conventional layout for libraries intended to be consumed by other projects.

Instead of exposing headers directly, it is generally recommended to organize them so that consumers can include them like this:

#include <project_name/header_name.h>

This helps avoid collisions if multiple libraries happen to provide a header with the same name. A generic:

#include <minmea.h>

is more likely to conflict than:

#include <minmea/minmea.h>

This convention also works well with package managers like vcpkg and CMake's FetchContent. From the consumer's perspective, these libraries are used as if they were installed system-wide, so following a standard include layout makes integration more predictable and consistent.

I first came across this recommendation in the first edition of Modern CMake for C++ by Rafał Świdziński. On page 96, it suggests structuring a library like this:

lib3/
├── include/
│   └── lib3/
│       └── public.h
├── test/
├── CMakeLists.txt
└── lib3.cpp

When the include/ directory is installed, the internal structure is preserved, so consumers can include the header as:

#include <lib3/public.h>

rather than:

#include <public.h>

So I think moving minmea.h under include/minmea/ would align the project with common CMake and C++ library conventions, especially if the library is intended to be distributed through package managers.

That said, I don't think this is strictly required if the project is intentionally kept as a single-header library; it is more about making the library easier to consume as it grows.

Also dear @kosma will appreciate it if you take a look at the pull request in vcpkg for this library:

microsoft/vcpkg#52281 (comment)

The following is a minimal example that fetches minmea from vcpkg:

CMakeLists.txt
main.cpp
CMakePresets.json
vcpkg.json

You can put all these in an empty directory and run:

cmake --preset linux-default-debug
cmake --build --preset linux-default-debug

Just make sure vcpkg is installed in ~/.vcpkg instead of ~/vcpkg. That's where my CMakePresets.json expect it to be.